-
-
Notifications
You must be signed in to change notification settings - Fork 12
ci: Some reorganization #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
a71c3ef to
30872a1
Compare
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
Can you setup |
|
I think it's ready for review, the only other part of getting the environment setup is:
|
More in line with current plugin template Also update github actions
Sorry, I just want to get some initial refactoring in order to have some more clean navigations of the project's actions. After the Qodana CI and build matrix, I will try help what I can and see what is broken
ci.yml,release.yml) and componentstest,test-ui,artifact-upload, etc. (Still not sure how to efficiently reuse the build artifacts, would need some info about thebuild/folder structure)ReleaseDraft? Issue is this model is not as available to outside contributors, I think it would be better to just have the artifacts for users to try useUnifyDeferredrelease.yml. Typically I make it run on git tag and be dependent on all tests prior to that, what is your opinion on that?